Proposed change

pywemo 1.1.0 includes some improvements for the Long Press feature on WeMo dimmers/switches. I've been running this version for about 2 weeks without issue on 2023.6.2 and on 2023.7.0 starting the same day it was released.

• Release notes: 1.1.0, 1.0.0, 0.9.2
• Changelog: pywemo/pywemo@0.9.1...1.1.0

All of the breaking changes from the pywemo 1.0.0 release were addressed in #46797, #72316, #72378, #72400, and #94791.

It would be nice if this could be included in a bug fix release for 2023.7.X, but it's also perfectly fine if it is included in a future monthly release too.

I'm expecting this to help with #75063. I suspect pywemo may have been triggering a bug in specific WeMo devices resulting in slow memory leak that eventually causes them to be in an unavailable state until the physical reset button is pressed. Attempting to more accurately replicate the exact UPnP messages generated by the devices seems to have helped on a WeMo dimmer of mine that was frequently becoming unavailable after 5-7 days. Its uptime is currently 3 weeks.

Those bug fixes are in pywemo==1.1.0. But, sometimes the issue takes a while to appear so it's hard to say with certainty that this fixes the issue. I have therefore not marked this PR as a fix for that issue. I'd like to see if the situation improves for others before closing the issue.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Belkin WeMo Device Unavailable & Then After Uninstalling/Reinstalling Integration, No Entities #75063
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.